Skip to content

Migrate to modern Python tooling (uv, pyproject.toml, semantic-release, src layout) - #2423

Open
salman2013 wants to merge 1 commit into
openedx:masterfrom
salman2013:modernize-python-tooling
Open

Migrate to modern Python tooling (uv, pyproject.toml, semantic-release, src layout)#2423
salman2013 wants to merge 1 commit into
openedx:masterfrom
salman2013:modernize-python-tooling

Conversation

@salman2013

@salman2013 salman2013 commented Jul 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

  • Phase 1 — Consolidate all package metadata into pyproject.toml (PEP 621): static dependencies, SPDX license, setuptools-scm for dynamic versioning, coverage config, isort config; delete setup.py, setup.cfg, .coveragerc
  • Phase 2 — Replace pip-tools with uv: [dependency-groups] (PEP 735), uv.lock, updated tox.ini to use tox-uv + uv-venv-lock-runner, updated Makefile and CI workflow to use uv sync/uv run tox
  • Phase 3 — Add python-semantic-release for automated versioning and PyPI publishing via OIDC trusted publisher; delete legacy pypi-publish.yml
  • Phase 4 — Migrate to src/ layout; update all filesystem path references in Makefile, webpack configs, karma, scripts, and settings

Test plan

  • CI passes on this PR (django42, django52, js, quality environments)
  • Configure OIDC trusted publisher on PyPI for openedx/edx-ora2 → workflow release.yml before merging

🤖 Generated with Claude Code

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Jul 17, 2026
@openedx-webhooks

openedx-webhooks commented Jul 17, 2026

Copy link
Copy Markdown

Thanks for the pull request, @salman2013!

This repository is currently maintained by @openedx/openedx-unmaintained.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@openedx-webhooks openedx-webhooks added the core contributor PR author is a Core Contributor (who may or may not have write access to this repo). label Jul 17, 2026
@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Jul 17, 2026
@codecov

codecov Bot commented Jul 17, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.05%. Comparing base (b60672e) to head (7d5e631).

Additional details and impacted files 
@@            Coverage Diff             @@
##           master    #2423      +/-   ##
==========================================
- Coverage   95.46%   95.05%   -0.42%     
==========================================
  Files         198      179      -19     
  Lines       22842    19991    -2851     
  Branches     1551     1442     -109     
==========================================
- Hits        21807    19002    -2805     
+ Misses        780      746      -34     
+ Partials      255      243      -12
Flag Coverage Δ
unittests 95.05% <100.00%> (-0.42%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@salman2013
salman2013 force-pushed the modernize-python-tooling branch from d6b467b to 5ae0ab5 Compare July 20, 2026 11:45
@itsjeyd itsjeyd moved this from Needs Triage to Waiting on Author in Contributions Jul 28, 2026
@itsjeyd

itsjeyd commented Jul 28, 2026

Copy link
Copy Markdown

Hi @salman2013, thank you for your contribution! Please let us know when it is ready for review.

@salman2013 salman2013 changed the title chore: migrate to modern Python tooling (uv, pyproject.toml, semantic-release, src layout) Migrate to modern Python tooling (uv, pyproject.toml, semantic-release, src layout) Sep 2, 2026
@salman2013
salman2013 force-pushed the modernize-python-tooling branch 2 times, most recently from fcf340f to 13c9e99 Compare September 2, 2026 08:49
@salman2013 @claude
build: modernize Python tooling (uv, pyproject.toml, semantic-release)
7d5e631 
- Migrate package metadata from setup.cfg/setup.py to pyproject.toml (PEP 621)
- Switch dependency management from pip-tools to uv with dependency groups
- Add python-semantic-release and commitlint workflows
- Fix JS tests, pylint, and leaderboard logging for uv editable installs
- Address review findings: tox-uv>=1, default-groups=[], vcs_release=false,
  GitHub Release step, ci.yml push trigger, MANIFEST.in hygiene
- Use uv sync --group doc for ReadTheDocs builds

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@salman2013
salman2013 force-pushed the modernize-python-tooling branch from 13c9e99 to 7d5e631 Compare September 2, 2026 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U

Projects

Contributions
Status: Waiting on Author

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@salman2013 @openedx-webhooks @itsjeyd